View ST7MDT1-DVP2US_1782572.PDF datasheet online --- IC-ON-LINE

Datasheet File OCR Text:

st7mdt1-dvp2 development kit user manual release 1.2 june 2001 ref: doc-st7mdt1-dvp2
use in life support devices or systems must be expressly authorized. stmicroelectronics products are not authorized for use as critical components in life support devices or systems without the express written approval of stmicroelectronics. as used herein: 1. life support devices or systems are those which (a) are intended for surgical implant into the body, or (b) support or sustain life, and whose failure to perform, when properly used in accordance with instructions for use provided with the product, can be reasonably expected to result in significant injury to the user. 2. a critical component is any component of a life support device or system whose failure to perform can reasonably be expected to cause the failure of the life support device or system, or to affect its safety or effectiveness. instructions for usewarning this product is conform to the 89/336/eec directive. it complies with the ite en55022 standard for emc emissions and generic 50082-1 (1992 edition) immunity standards. this product is an fcc class-a apparatus. in a residential environment, it may cause radioelectrical disturbances. in addition, this development board is not contained in an outer casing; consequently, it cannot be immune against electrostatic discharges (esd). it should therefore be handled only in static safe working areas. please refer to appendix a: emc conformity and safety requirements on page 59 for relevant safety information.
table of contents 3/74 chapter 1: introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5 1.1 development board functional configurations ............................................... 6 1.2 software and documentation for the development kit ................................... 8 1.3 about this manual.... ..................................................................................... 8 1.4 getting assistance ........................................................................................ 9 chapter 2: getting started . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11 2.1 your system requirements .......................................................................... 11 2.2 delivery checklist ........................................................................................ 11 2.3 installing the hardware ................................................................................ 13 chapter 3: stvd7 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15 3.1 installing stvd7 ......................................................................................... 15 3.2 launching stvd7 ....................................................................................... 16 3.3 about stvd7 debugging features .............................................................. 17 3.4 workspaces ................................................................................................ 18 3.5 toolchains and application files .................................................................. 19 3.6 creating a workspace ................................................................................. 22 3.7 opening an existing workspace .................................................................. 24 3.8 opening binary files .................................................................................... 26 3.9 changing your project settings ................................................................... 27 3.10 saving workspaces ..................................................................................... 29 3.11 debug context and build context ................................................................ 31 3.12 configuring the mcu .................................................................................. 32 3.13 start debugging! ......................................................................................... 37 chapter 4: programming st7 devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39 4.1 device programmer features ...................................................................... 40 4.2 programming methods ............................................................................... 40 4.3 device installation ....................................................................................... 41 4.4 starting the windows epromer ................................................................... 42 4.5 configuring the epromer ............................................................................. 43 chapter 5: hardware features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47 5.1 link to pc ................................................................................................... 47 5.2 jumper and solder point descriptions ......................................................... 47 5.3 power supply .............................................................................................. 48
table of contents 4/74 5.4 pin descriptions .......................................................................................... 48 5.5 on-chip peripherals .................................................................................... 51 5.6 hardware events ......................................................................................... 52 5.7 mdt1-dvp2 emulation features ................................................................. 55 appendix a: emc conformity and safety requirements . . . . . . . . . . . . . . . . 59 appendix b: troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61 b.1 identifying the problem ............................................................................... 61 b.2 changing the parallel port setup on your pc ............................................ 62 b.3 running the hardware test ........................................................................ 62 appendix c: glossary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65 product support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69 getting prepared before you call............................................................................... 69 contact list ................................................................................................................ 69 software updates ...................................................................................................... 70 hardware spare parts ............................................................................................... 70 index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71
st7mdt1-dvp2 user manual 1 - introduction 5/74 1 introduction thanks for choosing the st7mdt1-dvp2 development kit! the st7 dvp2 family of development kits offer the following new features: ? delivered with the debugger software packagest7 visual debug! ? trace buffer recording, viewing and output. ? in situ programming (isp) ability (for mcus that support this feature). this manual describes how to start and use the st7mdt1-dvp2 development kit for the st72254 series mcus, allowing you to get acquainted with the st7 microcontroller world and become familiar with the methods for developing and debugging st7-driven applications. note: if you come across any terms or abbreviations you do not understand, you can check their meaning in the glossary on page 65 . this manual also provides a guidance for programming a selection of flash, eprom and otp (one time programmable) st7 microcontrollers. the st7mdt1-dvp2 development kit contains all the necessary resources that will help you: ? design, develop and debug st7 application software running in a real environment, ? program selected st7 devices in a variety of modes (refer to ta bl e 3 on page 39). first off, check that the st7 mcu that you have picked for your application is in the list of devices supported by this version of the st7 mdt1-dvp2: supported devices st72254g1 st72254g2 st72216g1 st72215g2 st72104g1 st72104g2 st72251g1 st72251g2 st72213g1 st72212g2 st72101g1 st72101g2
1 - introduction st7mdt1-dvp2 user manual 6/74 the development kit can be used as a tool to emulate applications on the target mcu, or as a chip programming tool as summarized in the following sections. 1.1 development board functional configurations figure 1 shows the development board of the st7mdt1-dvp2 development kit in an st7 mcu emulator configuration. figure 2 shows the development board of the st7mdt1-dvp2 development kit in an st7 mcu programming board configuration. figure 1: using the development board as an st7 mcu emulator figure 3 shows how you can set up the development board to perform in situ programming of devices on an application board. parallel cable link emulated st7-mdt1 chip socket on application board 2 flat cables passive probe pc (running st7 visual debug) power supply user application board
st7mdt1-dvp2 user manual 1 - introduction 7/74 figure 2: using the development board as an st7 mcu programming board figure 3: using the development board for in situ programming (isp) parallel cable link sdip32 zif socket for programming st7mdt1-gp mcus so28 zif socket (available as an option) for programming st7mdt1-gp mcus power supply pc (running windows epromer) isp target connector target device to be programmed connect isp probe to isp target connector pc (running windows epromer) power supply user application board parallel cable link
1 - introduction st7mdt1-dvp2 user manual 8/74 1.2 software and documentation for the development kit the mcu on cd cd-rom contains: ? st7 tools, comprising the following software: - the source-level graphic debugger, stvd7, that operates with st7 development kits and st7-hds2 emulators or as a standalone st7 simulator. - the st7 assembly chain, composed of an assembler, linker, librarian and formatter. - the st7 windows epromer to program your mcu target devices. ? third-party c compiler and toolchain demos (hiware and cosmic). ? st7 application notes (with sources), training slides and exercises, this manual (in pdf version), and other useful reference documents in pdf format, such as: - datasheets for the st7 mcu family - st7 programming manual - st7 assembler-linker user manual - stvd7 user manual 1.3 about this manual.... detailed instructions on how to install your development kit configuration is described in chapter 2: getting started on page 11. how to start debugging your application using your development kit and stvd7 is described in chapter 3: stvd7 on page 15. how to program devices with the development kit is described in chapter 4: programming st7 devices on page 39. the development kits hardware features are described in chapter 5: hardware features on page 47. the following conventions are used in this manual: bold text highlights key terms, phrases and is used when referring to names of dialog boxes, windows and tabs within windows. bold italic text denotes menu commands (or sequence of commands), options, buttons or check boxes which you must click in order to perform an action.
st7mdt1-dvp2 user manual 1 - introduction 9/74 1.4 getting assistance for more information, application notes, faqs and software updates on all the st microcontroller families, check out the cd-rom or our website: http://mcu.st.com for assistance on all st microcontroller subjects, or if you need help with using your emulator, use the contact list provided in product support on page 69. well be glad to help you!
1 - introduction st7mdt1-dvp2 user manual 10/74
st7mdt1-dvp2 user manual 2 - getting started 11/74 2 getting started 2.1 your system requirements the st7mdt1-dvp2 development kit (both hardware and software components) has been designed to work with pcs meeting the following requirements: ? one of the following operating systems: microsoft ? windows ? 95, 98, 2000 or nt ? . ? intel ? pentium (or compatible) processor with minimum speed of 100 mhz. ? minimum ram of 32 mb. ? 21 mb of free hard disk space to install all of the st7 tools. 2.2 delivery checklist the st7mdt1-dvp2 development kit contains: 1 one development board (ref.: mb 269). 2 one parallel cable for pc connection. 3 one 5 v external dc power supply with female connector cable. 4 sdip32 passive probe (ref.: db 382) and two 34-pin flat cables. 5 an so28 probe adapter (ref.: db359) for user application connection. 6 one isp 10-pin flat cable for in situ programming. 7 one mcu on cd cd-rom (not shown). 8 this manual (not shown). (1) (2) (3) (4) (5) (6)
2 - getting started st7mdt1-dvp2 user manual 12/74 figure 4: development board layout 2 x 34-pin he10 application connectors sdip32 zif device programming socket so28 zif device programming socket (not provided with kit) trace probe inputs [2,1,0] isp mcu driver 10-pin in situ programming (isp) connector st72254 emulation chip push-button to simulate behavior of low voltage detection (lvd) cell of mcu during voltage drop. user application program status led (lights up red when running) if you wish to supply your application directly from the development board, via the application connector, place a solder spot here (g2 vcc app). max. 100 ma. emulation ram sticker with serial and version numbers. tp1 tp6 tp7 p2 ld1 jp1 u6 g2 g1 u9 u10 u15 u14 u20 u21 u22 j2 j3 u8 u12 u17 lvd rst w2 tp24 tp25 tp26 tp27 external trigger output external trigger input external clock input tp28 u18 u4 u5 u1 16 mhz clock ground plds eprom control ram board power on (green led) other power inlet) external power supply if you want to connect the emulator clock to oscout, place a solder spot here (g1). parallel port connector isp sel isp drv
st7mdt1-dvp2 user manual 2 - getting started 13/74 2.3 installing the hardware to install the hardware, follow these steps: 1 shut down and power-off the pc that is to be connected to the development board. 2 connect one end of the supplied parallel cable to the parallel connector (p2) on the development board. connect the other end of the parallel cable to the lpt1 or lpt2 parallel port on your pc. note: the supplied parallel cable has been tested in order to operate properly on most pcs. do not use any other cable, especially if it is longer than the one provided in the kitthe board may not operate properly. the cable should be connected directly to the db-25 female connector of the pc parallel port. this connector is similar to the one installed on the board. do not insert any additional cables or switch boxes between the pc and the board: a malfunctioning of the board may result. if a dongle is mounted on the pc parallel port, it should not interfere with the programming board. should you notice that the board is dysfunctional, remove the dongle and restart the installation procedure. 3 connect the passive probe to j2 and j3 on the development board using the two flat cables supplied with the development kit. 4 plug the dc power supply provided with the development kit into a power outlet. connect the power cable to the development board. the green power led will light up. note: the development board can also be fed via the jp1 connector by an external stabilized power supply (5 v 0.25 v, 1 a) not provided with the kit. if the board is fed via the jp1 two-point connector make sure that the right feeders lead to the right polarities. 5 power on the pc and proceed with the installation of the software (refer to chapter 3 on page 15). caution: do not use the jumper connections tp1, tp6 and tp7they are for factory testing only and modifications to them could cause your development board to malfunction. see section 5.2: jumper and solder point descriptions on page 47 for more information on the jumpers and solder points on your development board.
2 - getting started st7mdt1-dvp2 user manual 14/74
st7mdt1-dvp2 user manual 3 - stvd7 15/74 3 stvd7 stvd7 is an integrated development environment that allows you to edit, debug and rebuild your application all from within stvd7. the following sections tell you: ? section 3.1 how to install the stvd7 software, ? section 3.2 how to launch stvd7, ? section 3.3 a little about stvd7s debugging features, ? section 3.4 what a workspace is, ? section 3.5 what toolchains and executable files are supported by stvd7, ? section 3.6 how to create a stvd7 workspace, ? section 3.7 how to open existing workspaces, ? section 3.8 how to open binary files, ? section 3.9 how to change your project settings, ? section 3.10 how to save workspaces, ? section 3.11 how to switch from the build context to the debug context, ? section 3.12 how to configure the target mcu in order to debug more accurately and efficiently. 3.1 installing stvd7 your development kit comes with the mcu on cd cd-rom which contains a number of st7 software tools. these tools run under the windows ? 95, 98, 2000 and windows ? nt ? operating systems. note: to install the software on mcu on cd , windows ? 2000 and nt ? users must have administrator privileges. to install and setup the st7 software tools, follow these steps: 1 close all other open applications on your windows desktop. 2 insert the mcu on cd into your cd-rom drive. the cd-roms autorun feature will open up a welcome screen on your pc. if the autorun feature does not work, use windows ? explorer to browse to the cd-rom s root folder, and double-click on welcome.exe . 3 select install your development tools from the list of options. a new screen will appear listing the different families of stmicroelectronics mcus. 4 use your mouse to place the cursor over the st7 tools option. choose st tools , then st7 toolchain from the lists that appear. 2
3 - stvd7 st7mdt1-dvp2 user manual 16/74 5 the install wizard will be launched. follow the instructions that appear on the screen. you can choose to install the complete toolchain (i.e. the appropriate version of stvd7, the windows epromer and the assembler-linker) for each type of development tool (development kit, hds2 or emu3 emulators or simulator), or perform a customized installation. if you choose a customized installation, you can choose to install any or all of the stvd7 versions, and/or the windows epromer and/or the assembler- linker. as a minimum, in order to use your dvp , you must install stvd7 for dvp . if you also install the st7 assembly toolchain, you will be able to use the st7 assembly toolchain as part of stvd7s integrated development environment. the installation is now complete. you will be prompted to reboot your computer. you should do so before launching stvd7. 3.2 launching stvd7 1 from your windows desktop, select start>programs>st7 tool chain>development tools>stvd7 development kit. 2 the first time you open a version of stvd7 you will be prompted to enter the toolchain paths to be used by stvd7s integrated development environment. enter the paths for the toolchains that you use (i.e. any or all of the hiware, cosmic or st7 asm toolchains) and click ok . (the default paths for each toolchain are shown below.) 3 if you choose cancel, you will be prompted again to enter the toolchain paths the next time you launch stvd7. note: you may modify the toolchain path at any time from within stvd7simply select project>toolchain paths from the main menu to access the dialog box above.
st7mdt1-dvp2 user manual 3 - stvd7 17/74 3.3 about stvd7 debugging features a number of advanced features are included in the stvd7 software: ? data breakpoints on the occurrence of a memory access via a read operation or a write operation, or both. ? instruction breakpoints on the occurrence of an opcode fetch. ?a trace window to view the contents of the trace buffer , which permanently records in real time on 32-bits: - address and data bus information. - flag status and 4 external signal values. you can record up to 256 executed cycles. using trace filtering, you can filter out only those cycles you wish to record in the trace buffer. you can equally control which of the recorded cycles are displayed in the trace window using line filtering. addresses, data, control/status bits and 4 user signals are displayed using mnemonic and user symbols. ? hardware events can be used to control the trace recording or the sending of signals to the trigger outputs. ? a powerful online help facility can be invoked at any time to give additional information about the commands, the processor or the emulator kit.
3 - stvd7 st7mdt1-dvp2 user manual 18/74 3.4 workspaces stvd7 organizes project development and debugging into workspaces. workspaces allow you to store application and project settings and save them as a *.wsp file, so that each time you wish to work on the project, you will find all of the settings exactly as you left them. creating a workspace is the first thing that you need to do when using stvd7 for the first time or when starting any new project. you must have an open workspace to work with stvd7. how to create a new workspace is described in detail in section 3.6 on page 22. sample workspaces for each supported toolchain are provided so that you can familiarize yourself with stvd7 (for a listing of sample workspaces, see table 1 on page 20). each workspace is comprised of three information sets: the project settings, the visual environment and the debugging context. ? the project settings consists of the information necessary for a successful build of an application (commands to run, makefile file etc....). your workspaces project settings include the definition of your application toolchain (see section 3.5 on page 19). ? the visual environment consists of the open windows elements along with their current layout, bookmarks and other features. the visual environment is composed of two environments, one in the build context and one in the debug context (see section 3.11 on page 31). ? the debugging information includes information on breakpoints, memory mapping, advanced breakpoints programs, trace etc..
st7mdt1-dvp2 user manual 3 - stvd7 19/74 3.5 toolchains and application files a quick summary of development toolchains and application file types supported by stvd7 will help you in setting up your workspace. three different development toolchains are currently supported by the stvd7. each type of toolchain has its own application and executable file types, project environment and building tools (i.e. linkers and convertors): ? the st7 macroassembler toolchain from stmicroelectronics, which generates either .s19 or .hex executable files with various intermediate files, such as .map or .lst files. ? the hiware c or assembler toolchain , which generates .abs executable files with various intermediate files, such as .o or .dbg files. ? the cosmic c or assembler toolchain which generates .elf executable files with various intermediate files, such as .o or .st7 files. when you set up a workspace, you will need to define the following project settings: ? the toolchain to be used hiware, cosmic or st7 macroassembler. ? the executable file ( *.abs , *.elf , *.s19 or *.hex depending on toolchainrefer to ta bl e 2 on page 21). ? the maker program for the toolchain. the maker program can be a part of the toolchain software (such as hiwares maker.exe ) or you can choose to use a generic maker such as nmake.exe or gmake.exe (which is provided with the stvd7). ? the maker batch file ( *.mak or *.bat ). this is a file which you create for each application which spawns the compilation and/or link step each time you wish to build or rebuild. in it, you define the conditions for recompiling, re- linking or both. default *.mak or *.bat files are often included with the toolchainsfor example, maker.mak is included with the hiware toolchain and simply recompiles your application if it detects that the file has been saved since the start of your debugging session. the stvd7 software includes sample *.mak and/or *.bat files for each toolchainthese are listed in ta bl e 1 .
3 - stvd7 st7mdt1-dvp2 user manual 20/74 3.5.1 about executable files the user should verify that the options to include debug information were active during creation of the project files. table 2 on page 21 summarizes the way each toolchain functions and lists the different file types (source files, intermediate files and executable files) used and produced by the toolchain. the executable file types and intermediate file types necessary to exploit fully the stvd7 capabilities are listed. table 1: sample files included with stvd7 toolchain sample workspace (with default path sample make and/or batch files (with default path 1 ) description of make/batch file st macro assembler .../realtim/realtim.wsp .../realtim/tim_rtc.bat batch file that forces a recompile of the application. .../spim11/spim11.wsp .../spim11/spim11.bat batch file that forces a recompile of the application. cosmic .../c/cosmic/sample.wsp .../c/cosmic/sample.mak recompiles only if one (or more) of the application files has been resaved. .../c/cosmic/sample.bat batch file that forces a recompile of the application. hiware .../c/hiware/sample.wsp .../c/hiware/build.mak recompiles only if one (or more) of the application files has been resaved. .../c/hiware/rebuild.mak forces a recom- pile of the applica- tion. 1) the full default path is: c:/program files/stm/st7toolchain/stvd7/ dvp /sample/...
st7mdt1-dvp2 user manual 3 - stvd7 21/74 the executable file(s) , source files and any necessary intermediate files (these are listed above and contain debug information necessary to the stvd) should be located in the same project directory. you do this when you define your workspace. note: it is always preferable to have access to all of the files generated by the development toolchain. however, you can load *.s19 or *.hex binary files directly and have limited debugging capabilities (refer to section 3.8 on page 26). table 2: toolchain steps and their output files toolchain: st macroassembler hiware cosmic compile or assemble step: source file typ e s .asm .c, .asm .c, .s required options asm -li macrost7.asm +debug resulting file typ e s .obj, .lst .o, .dbg .o linker step: required options lyn macrost7.obj, macrost7 asm macrost7.asm -sym -fi=macrost7.map resulting file typ e s .map, .lst .abs .st7 converter step: obsend macrost7, f, macrost7.s19, srec or obsend macrost7, f, macrost7.hex, intel not applicable cvdwarf resulting executable file: .s19 or .hex .abs, .elf .elf necessary intermediate files: .map, .lst .o, .dbg
3 - stvd7 st7mdt1-dvp2 user manual 22/74 3.6 creating a workspace 1 select file>new workspace . this command opens a new window where you define the name of your workspace and the directory in which you want to work.
st7mdt1-dvp2 user manual 3 - stvd7 23/74 2 then, click next> . the new workspace: project settings dialog box appears: here you enter your software toolchain, your executable filename and your build parameters either by typing or using the drop boxes. 3 select the toolchain and enter the name of your applications executable file. for example, if you wish to use the hiware toolchain for st7, your executable file will be of type *.abs (refer to table 2 on page 21)click on the browse button to browse to the folder where your executable file is saved and select it. 4 next, choose the type of maker your application uses from the drop down list. in the example above, we have chosen the default hiware maker, maker.exe . stvd7 will automatically look for this maker file in the folder you defined as the hiware toolchain path. 5 finally, you must define a make file or a batch file. there are several sample files provided with stvd7 (see table 1 on page 20). here we have chosen
3 - stvd7 st7mdt1-dvp2 user manual 24/74 build.mak as the default make file, used when the build command is issued, and rebuild.mak as the make file to use when the rebuild command is issued. 6 after you have finished defining your project settings, click finish . once the workspace is opened, the workspace window displays its contents. when you create a new workspace, the first time you switch to debug context (see section 3.11 for an explanation of stvd7 contexts), the mcu configuration window will automatically open to prompt you to choose you target mcu and confirm or modify its option and memory configuration (see section 3.12 on page 32). 3.7 opening an existing workspace if you have already created a workspace, you simply need to open it in order to load all of your project settings into the stvd7. note: there are a number of sample workspaces provided with stvd7 that you can open to get familiar with stvd7. these samples are listed in ta ble 1 on page 20. 1 from the main menu, select file>open workspace. this command opens a window where you can browse to any folder you wish, and select an existing workspace.
st7mdt1-dvp2 user manual 3 - stvd7 25/74 2 the workspace window opens. when a workspace is opened, all of the predefined project settings are loaded into the stvd7. the workspace window will show a structured representation of the project. for example, mywork.wsp shows that it uses build.mak as the make file and sample.abs as the executable file. note: although the name of the executable file is shown in the workspace window, it has not yet been loaded into the emulation memorysee page 26 . if you click on the source directory tab, the window will show every source and intermediate file type ( *.c , *.s , *.asm , *.h or *.o ) in the selected directory. 3 if there are no source files shown in the source directory tab of the workspace window, or you wish to list additional files stored in another folder, you may browse to them by clicking the double click here... folder. the add source directory window pops up allowing you to enter or browse for a new directory,
3 - stvd7 st7mdt1-dvp2 user manual 26/74 and filter out the file types of interest. you may also choose to specify a directory that is relative to the workspace directory by clicking on the path relative to the workspace directory option. 4 to load the executable file, as well as any intermediate files, click the debug icon or the reset chip icon. the application and symbols will be loaded. before you can start debugging, you must set the target hardware device by configuring the mcu. 3.8 opening binary files if you do not have access to the source or intermediate files generated by a toolchain, you may also load *.abs , *.s19 , *.hex or *.elf files on their own using the open workspace command. note: the range of debugging features available when you open a binary file only will be very restricted. you will only have access to basic debugging windows, such as the disassembly and memory windows. 1 launch stvd7 and select file>open workspace from the main menu.
st7mdt1-dvp2 user manual 3 - stvd7 27/74 2 browse to the folder where your binary file is stored, and select st7 application files (*.abs, *.s19, *.hex, *.elf) in the files of type field. 3 select your binary file ( *.abs , *.s19 , *.hex or *.elf ) and click open . the binary code in the executable file will be loaded into stvd7 and you will be able to access the disassembly window. a workspace file (of the same name as the binary file, but with an extension .wsp ) will be created automatically. 3.9 changing your project settings the project menu contains the build and rebuild all commands you need to recompile your application after having made changes to it in the course of debugging. you may also access your project or toolchain settings in the event you wish to change them.
3 - stvd7 st7mdt1-dvp2 user manual 28/74 from the main menu, select project>project settings . you can change your settings here and continue running your application. when you exit stvd7, the system will ask you if you want to save these settings in the workspace you have been working in. if you choose yes , these will become your new workspace settings; if you choose no , these settings will be lost.
st7mdt1-dvp2 user manual 3 - stvd7 29/74 the toolchain path... item invokes the following window: in this window, you can define your builder and/or assembler paths. clicking opens a browser window. 3.10 saving workspaces whenever the current workspace is closed, it is automatically saved. this can happen either when exiting stvd or opening or creating a new workspace. in addition to this, a workspace can be explicitly saved with the file>save workspace... or file>save workspace as... commands. the user is given the choice of which of the workspace elements to include in the saved file. either the visual environment or the debugging information may be saved alone, or both may be saved together. this is configured as follows: 1 from the main menu, select tools>options . 2 in the options window that opens (see figure 5 on page 30 ), select the workspace tab. 3 choose whether you wish your saved workspace to include either the visual environment or the debugging information or both.
3 - stvd7 st7mdt1-dvp2 user manual 30/74 4 select which windows will appear docked when a project is opened by checking the appropriate check boxes in the floating windows in the main frame area. only windows currently docked in the main window can be included. 1 click apply to confirm your settings. 2 click ok close the dialog box. in addition, open file contexts and current window positions are saved when the workspace is closed. this feature restores the workspace window, window layout and file views to that which was current when stvd7 was closed. the toolbar layout, plus customized toolbar content is also saved and restored with the workspace (options set via the tabs entitled toolbars and commands ). by default (i.e. when saved automatically) the workspace is saved as file < application >. wsp . the name of the file corresponds to the name used for the executable file (for example, < application >. abs for a hiware executable file). figure 5: options window
st7mdt1-dvp2 user manual 3 - stvd7 31/74 note: using the configuration setup dialog box (available from the mcu configuration dialog box), you can also control what type of mcu configuration information is restored from a workspace file (*.wsp). 3.11 debug context and build context there are two stvd7 contexts, the build context and the debug context . until now, in creating a workspace, and defining your project settings, you have been in the build context. to proceed stepconfiguring your mcuyou need to change to the debug context. briefly, the two contexts are different in that: ? in the build context, you can open and close workspaces and build or re-build the application executable file. ? in the debug context you set the emulated mcu configuration (this step is described in section 3.12 on page 32) and debug the executable file created while in the build context. 3.11.1 build context the build context is the context set when starting stvd7. in this context, it is not necessary to be connected to a development kit and the debug commands are not available. you can also edit the source files of an application and perform the use the build command to perform compile and link actions in an interactive and iterative way to re-build the application executable file. 3.11.2 debug context in this context, the following debug actions can be carried out: ? loading, running and stopping the application. ? defining the mcu configuration (mcu options and memory mapping). ? viewing source and disassembled code. ? setting instruction breakpoints with a counter and/or condition. ? setting data breakpoints. ? viewing local variables, memory and st7 registers. ? viewing history of execution from the trace buffer or with the call stack feature analyzing the performance of a piece of code.
3 - stvd7 st7mdt1-dvp2 user manual 32/74 3.11.3 switching between contexts the switch between contexts usually occurs when the start debugging and stop debugging commands are used: from the main menu, choose debug>start debugging or stop debugging or click on the start debugging or stop debugging icons shown at right. while debugging, the editor allows source files to be modified. to switch to the build context perform either a build or rebuild action or use the stop debugging command. 3.12 configuring the mcu after you create or open a workspace, the next step you must perform before starting your stvd7 debugging session is to define and configure the target device (mcu) that you wish to emulate. the target device is defined and configured from the mcu configuration window. 1 first, ensure that you are in debug context by clicking on . (stvd7 has two contexts: debug context and build contextthese are described in section 3.11 .) note: the first time you enter into the debug context after having created a new workspace, the mcu configuration window will be opened automatically. 2 select tools>mcu configuration from the main menu. the mcu configuration window will open.
st7mdt1-dvp2 user manual 3 - stvd7 33/74 an example of a typical mcu configuration window is shown in figure 6 . note: the options shown in the above example may not be available for your particular target mcu. 3 set the target mcu . in the mcu name field, select the target device for which the application is intended from the dropdown box. once a target mcu has been chosen, the option configuration and the memory configuration fields will show the default values for this device. 4 configure the mcu options and on-chip peripherals. all of the configurable options on your target hardware device are listed in the option configuration fields. beside each option , a default value is given. you may change this value by clicking on it and choosing a new value from the drop down list. this allows you to configure your target devices options and on-chip peripherals. depending on the mcu selected, the default settings in the option configuration fields will change. it is up to you to configure those options that will impact your application so that the development kit accurately emulates your target device. figure 6: mcu configuration window option configuration fields memory configuration fields graphic memory configuration viewer mcu name field
3 - stvd7 st7mdt1-dvp2 user manual 34/74 note: for more information about the configurable options available on your target hardware device, please consult your target mcus datasheet. 5 configuring the mcu memory. the default memory settings depend on the mcu selected. however, you can configure the memory settings as you wish if your application requires non-default settings. this feature would enable you, for instance, to temporarily increase the rom size during the development phase of your application. there are two methods for configuring the memory settings on the mcu: by typing in the start and stop addresses of each memory zone into the memory configuration window , and by graphically moving the memory zone boundaries in the graphic memory configuration viewer (see page 36 for more instruction). memory zone types the left column of the memory configuration window indicates the address range of each memory zone. the right column indicates the memory type of each zone. depending on your target mcu, the available memory types may be: peripherals, ram, rom, stack, system, eeprom, reserved, vectors, memory configuration fields graphic memory configuration viewer
st7mdt1-dvp2 user manual 3 - stvd7 35/74 application. some of these zones can have their type and size modified, others cannot be modified. their definitions and properties are explained as follows: ? peripherals : microcontroller internal or rebuilt peripherals registers. their properties are defined as in the microcontroller datasheet. this memory cannot be modified. ? ram : random-access-memory of the microcontroller. this memory type can be modified. ? rom : read-only memory of the microcontroller. write protected. this memory type can be modified. ? stack : stack of the microcontroller. this memory type cannot be modified. ? system : the development kit uses this space for emulation management. this memory type cannot be modified. ? eeprom : this memory is internal to the microcontroller and is located inside the emulation device. the programming of this zone is done according to an automaton found in the datasheet. this memory type cannot be modified. ? reserved : this memory zone is reserved as on the microcontroller. it is not allocated to any use and is write protected. this memory type cannot be modified. ? vectors : this memory zone contains the user interrupt vectors zone. it is write protected. this memory type can be modified. ? application : this memory type is microcontroller-specific. the user can add memory or peripheral resources on its hardware. it is not available on every development kit. properties are linked to the user hardware. this memory type can be modified. for most target mcus, you may modify the following types of memory zone: ram , rom , reserved and application . this feature would enable you, for instance, to temporarily decrease the ram zone, increase the size of the rom (to exceed what is available on the real microcontroller) during the first stages of development. once your program is functional, you can start to optimize its size by reducing your code and returning these zones to their original size. there are two different actions you may perform on the memory configuration: ? change the type of an entire existing zone. ? define a new zone of any type wherever possible.
3 - stvd7 st7mdt1-dvp2 user manual 36/74 to change an existing memory zone: 1 select the memory zone to be modified. 2 click on the modify button at the bottom of the window. a new mcu memory range dialog box will open, allowing you to change either the address range and/or the memory type of the memory zone. to create a new zone of any type: 1 click on the insert button. the new mcu memory range dialog box will appear. 2 enter the address range of the new memory zone in the from and to fields. 3 select the type of the new memory zone in the type field. 4 click ok to validate your choice. the new memory zone will then appear in the mcu configuration window unless you tried to create a new zone in a non-modifiable memory space (such as stack or eeprom). to use the graphic memory configuration viewer: 1 in the memory configuration window, click on the zone whose boundaries you wish to move. 2 check the selection auto zoom box in the upper right-hand corner. the graphical view of the memory configuration will be scaled so that the zone you have selected is easily visible. 3 at the upper and lower boundary of the zone, at the left-hand side of the graphical viewer, you will see a small triangle and rectangular box giving the boundary addresses of the memory zone. you can change a boundary address by dragging and dropping the triangle with the mouse to its new location. the triangle can be moved either up or down, left or right in the graphical viewer.
st7mdt1-dvp2 user manual 3 - stvd7 37/74 the mcu configuration that you specify will, by default, be saved in a workspace file ( *.wsp ) for the project. the next time the application is opened, the stvd will automatically set the mcu configuration (as well as the layout of opened windows and other debug information) to the same conditions you had when you left the last debugging session. if you do not wish your mcu configuration information to be saved in the workspace file, you must alter the default configuration setup options by clicking on the conf... button. 3.13 start debugging! once in debug context , you are now ready to start debugging your applicationusing the development kit. full documentation on how to: ? control your stvd7 work environment ? use its integrated editor ? use the many debugging windows and features is available from the online help and the online stvd7 user manual, located under help in the main menu.
3 - stvd7 st7mdt1-dvp2 user manual 38/74
st7mdt1-dvp2 user manual 4 - programming st7 devices 39/74 4 programming st7 devices once bug-free and ready for operation, your application program needs to be transferred into an st7 mcu program space. with the st7mdt1-dvp2 development kit, you may program the mcus shown in table 3 . table 3: programmable devices supported device device group programmable memory type 1 1) for more information about the programmable memory for each target device, refer to the target devices datasheet. programming method(s) 2 2) for descriptions of programming methods, see programming methods on page 40. st 72254 g1 st 72254 g2 group 1 (based on st72254) eeprom zif sockets 3 and isp 3) all sdip32 packages are programmable using standard development kit. so28 packag- es can be programmed by adding the so28 zif socket to the footprint provided at u12. the enplas product reference for the socket (not supplied with the kit) is enplas ots28-1.27-04 . st 72216 g1 group 1 (based on st72254) eeprom zif sockets and isp st 72215 g2 group 1 (based on st72254) eeprom zif sockets and isp st 72104 g1 st 72104 g2 group 1 (based on st72254) eeprom zif sockets and isp st 72251 g1 st 72251 g2 group 2 (based on st72251) eprom and otprom zif sockets st 72213 g1 group 2 (based on st72251) eprom and otprom zif sockets st 72212 g2 group 2 (based on st72251) eprom and otprom zif sockets st 72101 g1 st 72101 g2 group 2 (based on st72251) eprom and otprom zif sockets
4 - programming st7 devices st7mdt1-dvp2 user manual 40/74 4.1 device programmer features figure 7: general eproming architecture 4.2 programming methods 4.2.1 zif sockets the st7mdt1-dvp2 development board is provided with a sdip32 zero insertion force (zif) socket which allows the programming of sdip32 packaged mcus. pc host pc parallel port interface 5 v = / 1a external power supply 12 v 5 v 3.3v lcx244 max7256a pld dc/dc converters st7mdt1-dvp2 mai n board pc parallel port connector sdip32 so28 lcx244 sdip32 so28 5v / 12v power control programming data / control bus zif programming sockets microcontrollers to program:
st7mdt1-dvp2 user manual 4 - programming st7 devices 41/74 a footprint is also provided on the development board, for the optional mounting of an so28 zif socket. the reference number for the so28 zif socket (not supplied with the kit) is enplas ots28-1.27-04 . 4.2.2 in situ programming in addition to classic mcu programming using zif sockets, the st7mdt1-dvp2 development kit is provided with an in situ programming (isp) functionality. this allows the user to program a target mcu mounted on an application board. note: only group 1 target devices (see page 39 ) support the isp functionality. in order to take advantage of the isp functionality, your application board must be designed to allow for in situ programming. only target mcus provided with a power supply of 5 v support the isp functionality. a provided 10-pin flat cable can be connected to the isp connector (ref: w2) at one end, and to an isp target connector which is contained on the application board. refer to the target devices datasheet for details on adding an isp connector to your application board. the windows epromer fully supports the isp functionality. 4.3 device installation caution: take care when placing the device into a socket so as not to damage the device or the board. never insert or remove devices when powered. devices are powered only during read or write operations. place the device into the zero insertion force (zif) socket mounted on the board (location u6 for sdip32 devices) with the erasure window on top and pin 1 matching the triangle with a 1 beside it on the board. 1 zif socket align dot on device (pin 1) with the triangle on board. target device erasure window
4 - programming st7 devices st7mdt1-dvp2 user manual 42/74 4.4 starting the windows epromer 1 to start the windows epromer (winee), select start>st7 tools>windows epromer . the epromer main window appears: click here to display the epromer configuration window note that as long as the programming board and the device to be programmed are not specified, the display area is blank.
st7mdt1-dvp2 user manual 4 - programming st7 devices 43/74 4.5 configuring the epromer follow these steps: 1 in the main window tool bar, click the icon to open the epromer configuration dialog box: 2 from the list, select the programming board for this st7mdt1-dvp2 development kit: st7mdt1-dvp2 . 3 select the parallel port (lpt1 or lpt2) on your pc to which the development board is connected. 4 click the select chip tab to display the list of the devices that can be programmed with this st7mdt1-dvp2 development kit.
4 - programming st7 devices st7mdt1-dvp2 user manual 44/74 the list box shown below appears. 5 from the list shown in the above dialog box, select the device to be programmed: note: only devices displayed with an isp suffix can be programmed using isp functionality. 6 click ok to confirm. the dialog box closes. the memory mapping of the specified device now appears in the display area of the main window. it is made up of ffs, as one may expect, since programming has not taken place yet. to view in turn the memory mapping of a selection of devices plugged in, open the configuration window again, then the select chip list box, and click apply . the display area of the main window changes while the list box stays open, for you to choose another chip if necessary. select your target device with the isp option if you wish to program your target device using in situ programming (isp)
st7mdt1-dvp2 user manual 4 - programming st7 devices 45/74 7 start your programming session. for more information on how to use the windows epromer, click the help command in the main menu bar. note: refer to programming methods on page 40 for details on which programming methods can be used with your target device. the name of the device to be programmed is displayed here details stored in the epromer buffer for the the eprom has been selected space corresponding to the currently selected tab progress bar (progress of the current task being executed by the epromer) cursor position in the display area origin of the display area contents information area display area
4 - programming st7 devices st7mdt1-dvp2 user manual 46/74
st7mdt1-dvp2 user manual 5 - hardware features 47/74 5 hardware features 5.1 link to pc the st7mdt1-dvp2 development board communicates with your pc via the p2 connector connected to the pc parallel port (lpt1 or lpt2). note: the parallel port of your pc should have been configured (in the bios settings) with either the centronics , epp , ecp or bidirectional parallel port configurations. 5.2 jumper and solder point descriptions the following table lists jumpers and solder points located on the development kit board, and whether they can be configured by the user, and if so, what they do. jumper name user- configurable? description of utility isp-sel (tp1) no use of this jumper could permanently damage the development board. this jumper has been removed from current versions of the st7mdt1-dvp2. isp drv prg (tp6) under very specific circumstances. on older st7mdt1-dvp2 development kit boards, you may need to use this jumper to perform an isp driver firmware patch as detailed in the application note an1363/0401, entitled workaround to isp mode limitation in st7mdt1-dvp2 and st7mdt2-dvp2 . do not attempt to use this jumper for isp mode programming! use of this jumper is only supported following the detailed instructions given in an1363/0401, available from sts website at http://mcu.st.com . in currently released version of the development kit, this jumper has been removed, as the isp mode limitation has been corrected. jam prog (tp7) no use of this jumper could permanently damage the development board. this jumper has been removed from current versions of the st7mdt1-dvp2. g1 yes soldering the two poles of this solder point together allows you to connect the clock to the osc_out pin on the passive probe connector. g2 yes soldering the two poles of this solder point together allows you to power your application board using the vdd pin in the passive probe connector (see section 5.3.2 on page 48)
5 - hardware features st7mdt1-dvp2 user manual 48/74 5.3 power supply 5.3.1 supplying the development kit a plug-in power supply pack is supplied with the st7mdt1-dvp2 development kit to be connected to the p1 male jack connector. this power supply must be plugged into the appropriate ac source. specific sales types indicate the corresponding mains ac voltage supported: provided dc power specifications are as follows: voltage: 5 v current: 1 a a complementary power supply inlet (ref.: jp1) is provided with the same specifications. when using this power supply, take care of the polarities marked nearby the two-point connector. 5.3.2 supplying the application board you may supply your application board directly from the development board via the vdd pin in the specific probe connector, after a solder spot has been placed in g2 on the development board. refer to pin assignments given in section 5.4 for the location of the vdd pin on each passive probe type. note that this method of supplying power to your application board is not recommended over an external application board power source. 5.4 pin descriptions you may connect an application board to the st7mdt1-dvp2 development board for evaluation or debugging in linked emulation mode. signals are transmitted via a passive probe to be plugged in the application board at the location of the emulated device. table 4 on page 49 shows the pin assignment for the passive probe connector on the application board. sales type ac mains voltage supported st7mdt1-dvp2/eu 220 v st7mdt1-dvp2/uk 240 v st7mdt1-dvp2/us 110 v
st7mdt1-dvp2 user manual 5 - hardware features 49/74 table 4: sdip32 passive probe pin assignments probe pin no. pin name/description probe pin no. pin name/description 1 reset 17 c2 port 2 oscin (osc1) 18 c1 port 3 oscout 1 (osc2) 19 c0 port 4 b7 port 20 a7 port 5 b6 port 21 a6 port 6 b5 port 22 a5 port 7 b4 port 23 a4 port 8 not used 24 not used 9 not used 25 not used 10 b3 port 26 a3 port 11 b2 port 27 a2 port 12 b1 port 28 a1 port 13 b0 port 29 a0 port 14 c5 port 30 not used (vpptest) 15 c4 port 31 vss (ground) 16 c3 port 32 vdd 2 1) the emulator clock is connected to oscout only when a solder spot is placed in g1 on the development board. 2) the emulator is only connected to vdd if a solder spot is placed in g2 on the development board. the application voltage can be either 3.3 to 5 v only.
5 - hardware features st7mdt1-dvp2 user manual 50/74 table 5: so28 passive probe pin assignments probe pin no. pin name/description probe pin no. pin name/description 1 reset 15 c2 port 2 oscin (osc1) 16 c1 port 3 oscout 1 (osc2) 17 c0 port 4 b7 port 18 a7 port 5 b6 port 19 a6 port 6 b5 port 20 a5 port 7 b4 port 21 a4 port 8 b3 port 22 a3 port 9 b2 port 23 a2 port 10 b1 port 24 a1 port 11 b0 port 25 a0 port 12 c5 port 26 not used (vpptest) 13 c4 port 27 vss (ground) 14 c3 port 28 vdd 2 1) the emulator clock is connected to oscout only when a solder spot is placed in g1 on the development board. 2) the emulator is only connected to vdd if a solder spot is placed in g2 on the development board. the application voltage can be either 3.3 to 5 v only.
st7mdt1-dvp2 user manual 5 - hardware features 51/74 5.5 on-chip peripherals you can configure certain on-chip peripherals in stvd7s mcu configuration dialog box (refer to section 3.6 on page 22) so that the emulator accurately emulates your target device. the following options are available on all supported target devices: clock you may choose the clock type (for example, on-board , external or on-chip ) as a microcontroller configuration option. note: the clock types available can vary depending on the target device. refer to section 5.7.1 on page 56 for an explanation of clock types available). the development board is shipped with a 16-mhz (ttl) on-board clock. you may also use an external clock (ttl-compatible, max. 16 mhz) whose signal is supplied via the mini wrapping pin extclk located on the board next to the passive probe flat connector (ref.: tp26). for group 1 mcus you may also choose an on-chip clock. note: in normal mode (miscellaneous register slow mode bit = 0), acceptable clockin frequencies can take any value between 16 mhz and 250 khz. in slow mode (miscellaneous register slow mode bit = 1), the extclk frequency must take values between 16 mhz and 8 mhz. note that the board cannot operate with clock signals received from the application board via the oscin pin of the probe. you must use the extclk inlet instead. however, the application board can use the development board clock via the oscout pin of the probe. in this case you must place a solder spot on g1 (see jumper and solder point descriptions on page 47). watchdog this option allows you to choose whether the watchdog timer is enabled by software or by hardware. refer to the datasheet for your st7 mcu for more information on the watchdog timer. the following options are only available on the following microcontrollers: st72254g1/g2, st72216g1, st72215g2, st7104g1/g2.
5 - hardware features st7mdt1-dvp2 user manual 52/74 mcu vdd allows you to set the supply voltage for the debugging session at either 5 v or 3.3 v. lvd 5 volt s allows you to enable ( on ) or disable ( off ) the lvd (low voltage detection). this option only works when mcu vdd is set to 5 v. in this case, the selected low voltage detection threshold will be 4.3 v. clock filter when on, the internal cell clock filter of the emulation chip is enabled. refer to the datasheet for your mcu for more information on the internal clock filter. ext it allows you to specify to which port(s) external interrupts will be attributed. ? it0:pa/it1:pb-pc means that external interruptions at level 0 (it0) will attributed to port a, while external interruptions at level 1 (it1) will be attributed to ports b and c. ? it0:pa-pc/it1:pb means that the external interruptions at level 0 (it0) will be attributed to ports a and c, while external interruptions at level 1 (it1) will be attributed to port b. halt and watchdog there are two options: reset and no reset . if this option is set to reset, when the watchdog is enabled and a halt instruction is encountered in the executable code, a chip reset will be performed. if this option is set to no reset, no chip reset will be performed. 5.6 hardware events hardware events are defined events used to control the trigger signal outputs and trace buffer recording. there are three types of hardware event: ? event on (evt_on) : the address where the event begins. ? event off (evt_off) : the address where the event ends. ? event hit (evt_hit) : the event is active for the cycles in which one particular address is accessed.
st7mdt1-dvp2 user manual 5 - hardware features 53/74 for information on how to insert hardware events, refer to the online help available with the stvd7. for more information on how to used hardware events to control the external output trigger ( trigout ) signal or the trace buffer filtering, refer to section 5.6.1 on page 53. 5.6.1 trigger/trace settings the trigger/trace settings dialog box (shown below), allows you choose a variety of options: ? select between two hardware event modes: trace filtering enabled or trace filtering disabled. in the first mode, the recording of the trace buffer is controlled using the same hardware events as those used to control the signals from the external output trigger. see below for details on the external output trigger, trigout . ? choose to enable the break on trigin option. for details on the input trigger, trigin , see below. ? choose to enable the break on trace overflow option. with this option enabled, once the trace buffer is full, the program is stopped. you may access the trigger/trace settings dialog box from the main stvd7 menu by selecting tools>trigger/trace settings , or by clicking the trigger/trace settings icon in the tools toolbar.
5 - hardware features st7mdt1-dvp2 user manual 54/74 5.6.2 external output trigger (trigout) the st7mdt1-dvp2 development board features a special outlet (called trigout ,) through which an external signal can be triggered out. the trigout pin is located on the board next to the passive probe flat connector (ref.:tp24). from the trigger/trace settings dialog box, you can choose the hardware event mode for the external signal ( evt_off/evt_on or evt_hit ). 5.6.3 input trigger (trigin) the st7mdt1-dvp2 development board provides a special inlet ( trigin , ref.:tp25) that can be used to transmit a signal to stop the execution of your application upon the occurrence of an external event ( break on trigin ). the break on trigin option is available in the trigger/trace settings dialog box shown above. if this option is selected, on reception of a rising edge signal from the trigin pin, the program is stopped after the execution of the current instruction. a schematic diagram is shown below: monitor application f cpu op code fetch trigin trigin active on rising edge
st7mdt1-dvp2 user manual 5 - hardware features 55/74 5.7 mdt1-dvp2 emulation features figure 8: emulation architecture user application board control bus pc host pc parallel port interface 5 v = / 1a 3.3v 16 mhz pld (1) max7256a (3.3v) on board clock dc/dc converter external power supply lcx244 lcx244 st72f254 qfp80 emulation package (5v / 3.3v) user i / o ram_1 (5v) ram_2 (5v) rom (5v) control ram not used emulation system ram system rom flex file system monitor code 64k multiplexed bus lcx373 lcx373 lcx245 address bus data bus data bus pld (2) flex10k10a (3.3v) control bus status bus fct244 ctrl / status bus isp connect or ispdata ispclk ispreset i spsel fct244 5v / 3.3v control ext.probes connector st7mdt1-dvp2 main board osc2 dvp passive probe probe0, probe1, probe2 extclk, trigin flex10k10a programming data - breakpoints settings - user memory mapping definitions - trigger out settings target ispsel ispdata ispclock ist/rst 64k 64k 64k user application area - program source - variables / stack system monitor area - variables / stack ram
5 - hardware features st7mdt1-dvp2 user manual 56/74 5.7.1 emulation functional limitations and discrepancies not all development kit features are available or applicable for all target mcus. supported target mcus are divided into two groups: the following is a list of functional limitations and discrepancies applicable when using the development kit as an emulator (as compared to the actual target device features): group 1 (based on st72c254) group 2 (based on st72251) st72254 g1/g2 st72216 g1 st72215 g2 st72104 g1/g2 st72251 g1/g2 st72212 g2 st72213 g1 st72101 g1/g2 emulation function/feature target device group limitation or discrepancy cpu clock options groups 1 & 2 you are required to select the clock option for your target device when using the development kit with the stvd7 (refer to page 51 for instructions on how to choose clock options). for target devices in group 1 , you can choose between three clock options: external , on-board or on-chip . ?the external option refers to a clock external to the development board (for example, a clock on the user application board), connected via the extclk pin. ? the on-board option refers to the on-board 16 mhz clock generator provided on the development board. ? the on-chip option refers to the internal rc oscillator of the cpu itself. for devices in group 2 , you may only choose between on-board and external clock options. the external rc and xrd resonator options are not available on the mdt1-dvp2 development board.
st7mdt1-dvp2 user manual 5 - hardware features 57/74 temperature tolerance groups 1 & 2 independent of the target device used, the very large temperature tolerance scope of the st72254 target device (-40 c to +85 c) is not applicable to the development board. the development board has been designed to function at ambient temperature. slow mode groups 1 & 2 slow mode will not have the same significance for devices in both groups. for devices in group 1 , the setting of this bit allows the use of another two bits to set the division rate of the cpu clock. for devices in group 2 , one bit in the miscellaneous register implies the division by 32 of the internal cpu clock frequency. for more information, refer to the definition of the miscellaneous register in the target device datasheet. low voltage detection group 1 for those target devices in group 1 , the low voltage detection (lvd) feature is supported only when the supply voltage is 5 v (refer to lv d 5volts on page 52 for more details). it is implemented using the on-board push button (see figure 4 on page 12) which causes the chip to reset. your application will be able to detect that the reset was caused by lvd by reading the lvdrf bit in the crsr register. note that if the lvd push button is used with a group 2 target device, the chip will be reset, but the reason for the reset will not be recorded in any register. supply voltage group 1 for target devices in group 1, the development board application supply voltage should take a value of either 3.3 or 5 v, as opposed to any voltage in the 3 to 5.5 v range for the actual target devices. (the only allowable supply voltage for group 2 devices is 5 v.) emulation function/feature target device group limitation or discrepancy
5 - hardware features st7mdt1-dvp2 user manual 58/74 analog to digital converter group 2 for those devices in group 2, the analog to digital converter cell will have a longer conversion time in emulation than for the actual target device. ports a7, a5, a3, a2, a1, a0 group 2 while the development kit allows you to set a push/pull configuration for these ports, this is not a supported feature on actual group 2 target devices. stack size group 2 the emulation chips stack is located between addresses 0x100 and 0x17f. while those target devices in group 1 also have the stack in this same location, the target devices in group 2 have their stack located between addresses 0x140 and 0x17f. this discrepancy between the emulation chip and group 2 target devices has the following repercussions during an emulation/debugging session: after a stack underflow break, the stack pointer (i.e. the sp register) will indicate the address 0x100 (and not 0x140 as would occur with the actual target device). after a stack overflow break, the stack pointer (i.e. the sp register) will indicate the address 0x13f (and not 0x17f as would occur with the actual target device). note that if a stack overflow break is not validated, any overflow of the stack will erase user variables (if any) situated between addresses 0x100 and 0x13f inclusive. emulation function/feature target device group limitation or discrepancy
st7mdt1-dvp2 user manual appendix a: emc conformity and safety requirements 59/74 appendix a: emc conformity and safety requirements this development board respects the emc requirements of the european guideline 89/336/eec under the following conditions: ? any tester, equipment, or tool used at any production step or for any manipulation of semi-conductor devices have its shield connected to ground. ? all ferrites provided with the development kit must be attached as described in the hardware installation instructions of the relevant user manual(s). ? your development board must be placed on a conductive table top, made of steel or clean aluminumor covered by an antistatic surface (superficial resistivity equal to or higher than 0.5 m w /cm 2 ), grounded through a ground cable(conductive cable from protected equipment to ground isolated through a 1m w resistor placed in series). all manipulation of finished goods be made at such a grounded worktable. ? the worktable must be free of all non-antistatic plastic objects. ? an antistatic floor covering grounded through a conductive ground cable (with serial resistor between 0.9 and 1.5 m w ) should be used. ? it is recommended that you wear an antistatic wrist or ankle strap, connected to the antistatic floor covering or to the grounded equipment. ? if no antistatic wrist or ankle strap is worn, before each manipulation of the powered-on development board, you touch the surface of the grounded worktable. ? it is recommended that antistatic gloves or finger coats be worn. ? it is recommended that nylon clothing be avoided while performing any manipulation of parts.
appendix a: emc conformity and safety requirements st7mdt1-dvp2 user manual 60/74
st7mdt1-dvp2 user manual appendix b: troubleshooting 61/74 appendix b:troubleshooting b.1 identifying the problem if... then... error message (when starting the stvd7 for dvp): connection error (lpt1): interconnection failure. verify your input/output cable. ensure that: ? the parallel cable is connected between the development board and one of the pcs parallel ports (lpt1 or lpt2). note that the use of switch boxes between the parallel port connector of your pc and the development board is not recommended. ? the development board is powered on. ? the parallel cable used is the one supplied with the kit by stmicroelectronics. ? stvd7 and windows epromer are not running at the same time. if this is the case then shut down both and ensure that only one or the other is running at any one time. if none of the above items has been overlooked, this may mean that your parallel port connection needs to be reconfigured. please refer to section b.2 , below. error message (during stvd7 session): emulator power off has been detected. ensure that your development board is powered on and shutdown and restart your stvd7 session. isp does not work. certain application board configurations may prevent you from being able to program your target mcu using isp mode. ensure that: ? the target mcu mounted on your application board has a power supply of 5 v. ? there is low capacitance on the mcus r eset pin. if you still cannot get isp to work using your dvp, consult the application note an1363/0401 entitled workaround to isp mode limitation on the st7mdt1-dvp2 and st7mdt2-dvp2 which can be found on sts website at: http://mcu.st.com this application note describes how to download and perform a software and hardware patch that will permit you to use isp programming even when you have high capacitance on the reset pin of your target device.
appendix b: troubleshooting st7mdt1-dvp2 user manual 62/74 b.2 changing the parallel port setup on your pc under certain circumstances, you may receive the following error message: connection error (lpt1/lpt2): interconnection failure. verify your input/ output cable. this may mean that the setup of the lpt1 or lpt2 port on your pc is not compatible with the st7mdt1-dvp2 development board. to set up the port correctly: 1 shut down and restart your pc in order to enter the bios setup. 2 follow the messages displayed on the screen and when prompted, press the key required to enter the bios setup (usually a function key or the esc key). 3 select the parallel ports menu. (this may be listed under i/o ports.) 4 change the mode of the lpt port that you have connected the development board to (i.e. either lpt1 or lpt2) to one of the following compatible modes, according to the following table: 5 save your changes and exit the bios setup. b.3 running the hardware test the hardware test in the stvd7 for dvp lets you check that your development board is correctly connected, configured and working. you can test components of the development board individually, or all at the same time. if problems occur during debugging (such as bad debugger responses and unexpected behavior), you should check for hardware problems using the hardware test function, and if any are detected, contact your stmicroelectronics sales representative (see product support on page 69). you may open the hardware test dialog box by: ? selecting, from the main menu, emulator>hardware test operating system compatible parallel port modes windows 95 ecp, epp, bidirectional or centronics windows 98 epp, bidirectional or centronics windows nt4 ecp, epp, bidirectional or centronics
st7mdt1-dvp2 user manual appendix b: troubleshooting 63/74 ? clicking on the hardware test icon in the emulator toolbar. caution: be cautious in performing a hardware test on the emulator while an application is open. the opened application will be corrupted by the hardware testing process. if you find that your application has been corrupted, simply close the application, and reopen it. the hardware test dialog box shows a list of different tests that can be performed on the development board. check the box of each test that you wish to perform (they are all checked by default) and click apply to start the hardware test.
appendix b: troubleshooting st7mdt1-dvp2 user manual 64/74 the hardware tests will be performed one by one, and the results summarized in the dialog box as shown at right:
st7mdt1-dvp2 user manual appendix c: glossary 65/74 appendix c:glossary development board the main component of the development kit, the development board consists primarily of a cpu which is capable of emulating the family of mcus supported by the development kit, and a number of peripherals that allow you to perform debugging and programming functions. the development board contains a parallel port to communicate with your pc and so allow the running and debugging of applications designed for your target mcu. there are trigin, trigout and trace probe pins to respectively input and output signals. there are also a variety of means by which you can use the development board to program target mcu devices: via the on-board sdip32 socket, via the in situ programming (isp) port, and optionally, by installing a s028 programming socket. dil dual in line. designates a type of device package with two rows of pins for thru- hole mounting. sometimes also called dip (dual in-line package). ecp extended capabilities port communication standard. eeprom electrically erasable programmable read-only memory. a non-volatile type of memory that can be erased and reprogrammed by program instructions. since no special power supplies or ultra-violet light source is needed, the contents of this kind of memory can be changed without removing the mcu from the application system. epp enhanced parallel port communication standard. eprom erasable programmable read-only memory. a non-volatile type of memory that can be erased by exposure to an ultra-violet light source. mcus that have eprom are easily recognized because the package has a quartz window to allow exposure to the uv light. if the eprom mcu is packaged in an opaque plastic package, it is called a one-time programmable otp mcu because there is no way to expose the eprom to a uv light source.
appendix c: glossary st7mdt1-dvp2 user manual 66/74 footprint designates the dimensions of the location of a component on a printed circuit board or in a socket. it depends on the number of pins, their size, type and positioning. the footprint of each st7 device is specified in the datasheet in the section titled package mechanical data. (refer to the st7 mcu family databook or the datasheets provided on the mcu on cd cd-rom). lv d low voltage detection. this is a feature available on some of the st7 mcus supported by the st7mdt1-dvp2 (i.e. those in group 1refer to section 5.7.1 on page 56). a lvd push button on the development board allows you to simulate what occurs when the mcu detects that the supply voltage is below a given threshold. isp in situ programming. provided you have an in situ programming connector on the application board containing the target device, you can use the st7mdt1-dvp2 isp functionality and the windows epromer to directly program the target device. note that not all st7 mcus support the isp functionality. refer to in situ programming on page 41 for more details. mcu microcontroller unit. otherwise referred to as the target device throughout this manual. this is the core product (or family of products) for which the development kit is designed to act as an emulator and programming tool. in general terms, an mcu is a complete computer system, including a cpu, memory, a clock oscillator and i/o on a single integrated circuit. otp one time programmable. also referred to as otprom (one time programmable read-only memory). a non-volatile type of memory that can be programmed but cannot be erased. an otp rom is an eprom mcu that is packaged in an opaque plastic packageit is called a one-time programmable mcu because there is no way to expose the eprom to a uv light source. passive probe a printed card having connector pins that allow you to connect the st7mdt1- dvp2 to the mcu socket of the user application board. using the passive probe allows the development board to emulate a target device embedded in your
st7mdt1-dvp2 user manual appendix c: glossary 67/74 application. the passive probe is connected to the development board by two flat 34-pin cables. pc (program counter) the program counter is the cpu register that holds the address of the next instruction or operand that the cpu will use. rc network resistor-capacitor network. so small outline. designates a type of device package with two rows of pins for smd or socket mounting. stvd7 (st7 visual debug) a graphic debugger software package that allows you to debug applications destined for the st7 family of mcus, either using a built-in simulator function, the mdt1-dvp development kit or an hds emulator. target device this is the st7 device that you wish to use in your application, and which the development kit will emulate for you. user application board designates your application board. it should include a socket for inserting the st7 device or the passive probe. zif socket zero insertion force socket. this type of programming socket is mounted directly on the development board. to program an mcu, you insert it into the appropriate socket (i.e. the sdip32 zif socket for sdip32 packages, or, if installed, the so28 zif socket for so28 packages).
appendix c: glossary st7mdt1-dvp2 user manual 68/74
st7mdt1-dvp2 user manual product support 69/74 product support if you experience any problems with this product or if you need spare parts or repair, contact the distributor or st sales office where you purchased the product. getting prepared before you call collect the following information about the product before contacting st or your distributor: 1 name of the company where you purchased the development kit. 2 date of purchase. 3 order code: refer to the side of your developmentkit box. the order code will depend on the region for which it was ordered (i.e. the uk, continental europe or the usa). 4 serial number: the serial number is located on a label on the developmentboard. 5 target device: the sales type of the st7 microcontroller you are using in your development. contact list note: for american and canadian customers seeking technical support the us/canada is split in 3 territories. according to your area, contact the following sales office and ask to be transferred to an 8-bit microcontroller field applications engineer (fae). canada and east coast stmicroelectronics lexington corporate center 10 maguire road, building 1, 3rd floor lexington, ma 02421 phone: 781-402-2650 mid west stmicroelectronics 1300 east woodfield road, suite 410 schaumburg, il 60173 phone: 847-517-1890
product support st7mdt1-dvp2 user manual 70/74 west coast stmicroelectronics, inc. 30101 agoura court suite 118 agoura hills, ca 91301 phone: 818-865-6850 europe france (33-1) 47407575 germany (49-89) 460060 u.k. (44-1628) 890800 asia/pacific region japan (81-3) 3280-4120 hong-kong (852) 2861 5700 sydney (61-2) 9580 3811 taipei (886-2) 2378-8088 software updates you can get software updates from the st internet web site http://mcu.st.com . for information on firmware and hardware revisions, call your distributor or st using the contact list given above. hardware spare parts yamaichi sockets you can order additional yamaichi qfp sockets directly from yamaichi at: http://www.yamaichi.de/pu/quad_flat_pack/spec/a21-ic149.htm
index 71/74 a analog/digital conversion limitations of .............................................. 58 c clock external ..................................................... 51 internal ...................................................... 51 normal mode ............................................. 51 option limitations ....................................... 56 slow mode................................................. 51 type ........................................................... 51 complementary power supply ........................... 48 d development board connecting to pc....................................... 13 definition of................................................ 65 eproming architecture ............................... 40 jumpers and solder points......................... 47 layout ........................................................ 12 development kit as device programmer .............................. 40 delivery checklist....................................... 11 emulation architecture............................... 55 emulation features .................................... 55 emulation limitations/discrepancies .......... 56 functions of.................................................. 6 system requirements................................. 11 e ecp definition of................................................ 65 emulation limitations/discrepancies .................. 56 emulator kit installing software for ................................ 15 software and documentation for.................. 8 epromer extclk pin ...................................................... 51 f finished goods manipulation of ......................................... 59 safety requirements .................................. 59 h hardware installing.................................................... 13 linking to pc ............................................. 47 power supply ............................................ 48 hardware events (see st7 visual debug) hardware test.................................................... 62 i in situ programming (see isp) installation stvd7 ...................................................... 15 isp.................................................................... 41 definition of ............................................... 66 j jumper descriptions .......................................... 47 l load binary files ................................................ 26 low voltage detection limitations of.............................................. 57 m mcu supported types .......................................... 5 mcu configuration............................................ 32 mcu memory configuring ................................................ 34 types ......................................................... 34 miscellaneous register ...................................... 51 o otp definition of ............................................... 66 index
index 72/74 p parallel port troubleshooting connection problems ....... 62 parallel port of your pc ..................................... 47 passive probe definition of................................................ 66 general configuration .................................. 6 parts reference.......................................... 11 pc parallel port ................................................. 47 peripherals configuring target ...................................... 33 ports limitations of .............................................. 58 power supply..................................................... 48 complementary ......................................... 48 programming device installation...................................... 41 eproming architecture ............................... 40 project settings modifying................................................... 27 r rom size .......................................................... 34 s slow mode......................................................... 51 limitations of .............................................. 57 software updates ..................................................... 70 solder point descriptions ................................... 47 st7 visual debug hardware events ....................................... 52 trigger/trace settings ................................. 53 stvd7 about ......................................................... 17 build context.............................................. 31 contexts..................................................... 31 creating a workspace ................................ 22 debug mode .............................................. 31 installing .................................................... 15 main features ............................................ 17 mcu configuration .................................... 32 opening binary files ................................... 26 opening workspaces................................. 24 supported application files ........................ 19 supported toolchains ................................ 19 switching between contexts...................... 32 toolchain paths ......................................... 16 workspaces............................................... 18 supply voltage limitations of.............................................. 57 support contact numbers for.................................. 69 for development kit ................................... 69 t target device definition of ............................................... 67 groups of supported.................................. 56 programmable memory types................... 39 programming methods.............................. 39 target devices supported.................................................... 5 temperature tolerance limitations of.............................................. 57 trigger/trace settings (see st7 visual debug) triggers external output (trigout) ...................... 54 input (trigin) .......................................... 54 trigin ............................................................. 54 trigout ......................................................... 54 troubleshooting ................................................. 61 connection error........................................ 61 u user application board definition of ............................................... 67 uses for development board ............................... 6 w windows epromer configuring ................................................ 43 getting started........................................... 42 winee (see windows epromer) workspaces creating new ............................................. 22 saving ....................................................... 29
index 73/74 z zif socket definition of ............................................... 67 zif sockets ....................................................... 40
information furnished is believed to be accurate and reliable. however, stmicroelectronics assumes no responsibility for the consequences of use of such information nor for any infringement of patents or other rights of third parties which may result f rom its use. no license is granted by implication or otherwise under any patent or patent rights of stmicroelectronics. specifications menti oned in this publication are subject to change without notice. this publication supersedes and replaces all information previously supplied. stmicroelectronics products are not authorized for use as critical components in life support devices or systems without the ex press written approval of stmicroelectronics. the st logo is a registered trademark of stmicroelectronics. intel ? is a u.s. registered trademark of intel corporation. microsoft ? , windows ? and windows nt ? are u.s. registered trademarks of microsoft corporation. ? 2001 stmicroelectronics - all rights reserved. purchase of i 2 c components by stmicroelectronics conveys a license under the philips i 2 c patent. rights to use these components in an i 2 c system is granted provided that the system conforms to the i 2 c standard specification as defined by philips. stmicroelectronics group of companies australia - brazil - china - finland - france - germany - hong kong - india - italy - japan - malaysia - malta - morocco - sin gapore - spain sweden - switzerland - united kingdom - u.s.a. http://www.st.com 7 4

▲Up To Search▲

Price & Availability of ST7MDT1-DVP2US

	To Download ST7MDT1-DVP2US Datasheet File
If you can't view the Datasheet, Please click here to try to view without PDF Reader .